The concept of software failure mode and effects analysis (FMEA) has grown in attractiveness over recent years as a way of assessing the reliability of software. Like its hardware counterpart, software FMEA is immensely tedious for an engineer to perform, as well as being error-prone. This paper presents the implementation of a novel method for automating code-level software FMEA based on treat...

Several reliability engineering approaches have been proposed to identify and recover from failures. A well-known and mature approach is the Failure Mode and Effect Analysis (FMEA) method that is usually utilized together with Fault Tree Analysis (FTA) to analyze and diagnose the causes of failures. Unfortunately, both approaches seem to have primarily focused on failures of hardware components...

The paper presents work in progress aiming at extending Failure-modes-and-effects Analysis (FMEA) to include embedded software. It is based on the insight that requirements on Software FMEA in this context are only dependent on the required functionality of the physical system, which, in particular, allows the consideration of a finite set of qualitatively characterized software failures.

Failure Mode and Effects Analysis is widely used in engineering hardware systems to help in understanding the effects of potential failures and the faults that cause them to occur. The analysis is iterative leading to improvements in the design until the risks associated with potential failure modes are reduced to an acceptable level. Interest in applying the technique to software has increased...

Failure Mode and Effects Analysis (FMEA) is a widely used dependability and safety technique aiming at systematically identifying failure modes, their causes, their effects, and the countermeasures that could mitigate their impact. Although FMEA has been thought for hardware, its use is also advocated for software (SW-FMEA). However, this involves several major hurdles such as the complexity of...

Technical systems are prevalent in many areas of our society. Nowadays they often include a considerable amount of software. Identification and avoidance of technical risks is of major importance in the development of these softwareintensive technical systems. A powerful analysis technique in the development process for technical systems is the Failure Mode and Effects Analysis (FMEA). This tec...

Abstract Practical uses of Failure Modes and Effects Analysis (FMEA) range from the identification of potential design defects and safety hazards, to maintenance planning, diagnostics and Prognostics and Health Management (PHM). According to the broadly accepted standard for FMEA, MIL-STD-1629A, a successful FMEA is one that conducted in a timely manner, so that the results can be used to ident...

The advancement and proliferation of information technology has made it possible for specified functions of systems including safety-critical systems to be software driven. Traditional failure analysis techniques existed before computers and are widely used in the failure analysis of hardware. Typically, hardware failures are random while software failures are systematic and this makes software...

Functional safety standards (ISO 26262, IEC 61508) require a safety life cycle which demands additional design and engineering tasks to be managed. This paper addresses how the existing FMEAs have to be extended and refocused to address and overview signal paths throughout the system. The safety standards require to classify signals with a SIL (Safety Integrity Level) and the higher the SIL the...

The technological advances in electronic and software have been rapidly assimilated by computer systems, demanding new approaches for software and systems engineering to provide reliable products, under well-known quality criteria. In this context, requirements engineering has a strategic role in project development. Problems in the elicitation activity contribute to producing poor, inadequate ...